Magnum One

home *** CD-ROM | disk | FTP | other *** search

/ Magnum One / Magnum One (Mid-American Digital) (Disc Manufacturing).iso / d20 / rfa200.arc / RFA.DOC < prev next >

Wrap

Text File | 1991-07-13 | 89KB | 3,057 lines

]]]]]]]]]] ]]]]]]]]]]] ]]]]]]]]] ]]]] ]]] ]]]]]]]]]]] ]] ]]]] ]]]] ]]] ]]]] ] ]] ]]]] ]]]] ]]] ]]]] ]] ]]]] ]]]] ]]] ]]]] ]] ]]]] ]]]] ]]] ]]]] ] ]] ]]]] ]]]]]]]]]] ]]]]]]]] ]]]]]]]]]]] ]]]]]] ]]]]]]]] ]]]]]]]]]]]] ]]]] ]] ]]]] ] ]] ]]]] ]]]] ]]] ]]]] ]]] ]]]] ]]]] ]]] ]]]] ]]] ]]]] ]]]] ]]] ]]]] ]]] ]]]] ]]]] ]] ]]]] ]]] ]]]] ]]]] ]]] ]]]] ]]] ]]]] ]]]] ]] ]]]] ]]] ]]]] ]]]] ]]] ]]]]] ]]] ]]]]] R F A <-> Remote file Administrator R F A <-> Remote file Administrator R F A <-> Remote file Administrator Written by MEG from System69 Software Development Group Written by MEG from System69 Software Development Group Written by MEG from System69 Software Development Group T A B L E O F C O N T E N T S T A B L E O F C O N T E N T S T A B L E O F C O N T E N T S ________________________________ ________________________________ ________________________________ 1. Rights (legal stuff)...............................3 2. What'sa RFA?.......................................4 3. Warranty (or lack of it)...........................5 4. Hardware and software minimal requirements.........6 5. Getting started....................................7 6. Installation.......................................10 7. Internal RFA commands..............................20 8. The TXT files......................................34 9. Macro and DOS......................................36 10. Limits.............................................41 11. Security...........................................42 12. Contributions and bug reports......................43 13. Acknowledgements...................................44 A. Access levels......................................46 B. Index..............................................48 NOTE: throughout this document, the system (node or point) where RFA is installed is referred as BOSS. RFA 2.00 - User's manual 3 ________________________________________________________________ 1. Rights (legal stuff) 1. Rights (legal stuff) 1. Rights (legal stuff) RFA is distributed as SHAREWARE, so it can be freely copied, provided that it remains in the original form. You can test RFA for a month, then you must send a contribution to S69 S.D.G. (see REG.DOC) and the order form filled with your data. You will receive a code and the personal key that you can insert in GINFO.RFA (see Chapter 6), to have your system running as an OWNER. S69 ensures you that EVERY contribution will be used to improve the development of Public Domain and Shareware software. Registered users will also be notified when a new major version of RFA is available. RFA 2.00 - User's manual 4 ________________________________________________________________ 2. What'sa RFA? 2. What'sa RFA? 2. What'sa RFA? Best definition I can find for RFA is: a command interpreter, using netmail messages as I/O channel. In other words, when RFA runs it scans the Netmail, localizing messages directed to it, and executes command listed in them. RFA offers you a lot of commands (see Chapter 7) but you can add more, using DOS commands in a way similar to batch files: the difference is that RFA commands have access levels and a security levels to protect the BOSS from hackers of ill-intentioned regular users. Using RFA the Sysop can also let points to handle file areas, granting the usage of powerful commands as COPY, TYPE, DEL and more, but ONLY in a set of pre-defined areas, without compromise the system security. Moreover, RFA offers a complete, versatile and easily adjournable information system that allows every user "Netmail capable" to know about the files availables on your system. RFA 2.00 - User's manual 5 ________________________________________________________________ 3. Warranty (or lack of it) 3. Warranty (or lack of it) 3. Warranty (or lack of it) "There once was a man who believed he never made mistakes. But he was wrong. And that's why we have debuggers". (Turbo Debugger User's Guide - Borland Intl.) The only warranty offered with RFA is that it occupies space on disk. I absolutely cannot assure that RFA will function or that it will be the solution to every problem. I ensure you that RFA is not a virus and that it does not contain trojan horses, backdoors or similar awful things (unless the program was infected after compilation). S69 S.D.G. refuses every liability, directed or indirected, included but not limited to material and moral loss derived from usage of RFA. RFA 2.00 - User's manual 6 ________________________________________________________________ 4. Hardware and software minimal requirements 4. Hardware and software minimal requirements 4. Hardware and software minimal requirements RFA only works on Opus and RA/QBBS (or compatible) Netmail base. If you use another format, you will need a converter to export netmail messages from your base to RFA base and back. RFA has no particular hardware or software requirements: it will work with every MS-DOS or PC-DOS operating system (version 3.00 or higher), with at least 200 KB of RAM; more RAM is required for Dos shells if you use DOS or ADOS commands, or macros (see la- ter). RFA 2.00 - User's manual 7 ________________________________________________________________ 5. Getting started 5. Getting started 5. Getting started RFA is easy to use with Netmail messages. For example, suppose that the point 2:332/102.6 (with password PWD1 for the RFA in- stalled on node 2:332/102) wants to receive the file list of area MSGAMES and the list of available areas. The point should simply address a Netmail message to RFA as follows: From: Maurizio Giunti of 332/102.6 From: Maurizio Giunti of 332/102.6 From: Maurizio Giunti of 332/102.6 To: RFA of 332/102.0 To: RFA of 332/102.0 To: RFA of 332/102.0 Subject: PWD1 Subject: PWD1 Subject: PWD1 FLIST $MSGAMES FLIST $MSGAMES FLIST $MSGAMES ALIST ALIST ALIST END END END When RFA receives this message, if the password matches and the point's access levels allow the execution of the commands, it creates an answer message adressed to point 332/102.6 that con- tains a list of files in area MSGAMES, and the list of available areas with relative access levels (see Chapter 7 for a detailed explanation of commands). The END command warns RFA that the executable part of the message is terminated; it can be omitted or substituted with a tearline (three subsequent "-"). Notice that, as in batch files, commands are executed in the same order they were inserted. Every user that can send Netmail messages can also use RFA, so it is very important, for safety of your system, to understand how RFA 2.00 - User's manual 8 ________________________________________________________________ to limit the users' "power". Before the execution of a command, RFA checks if the command is available for the user that reque- sted it: every user, in facts, has a command security level (said command security level command security level Clvl). Since every command also has a security level, RFA will only execute commands which level is EQUAL TO or LOWER THAN Clvl. In a similar manner, the user has an area access level, said area access level area access level Alvl, and RFA will show to the user informations only about areas with a level equal to or lower than Alvl. Access and security levels can be assigned during installation, as will become clear later. In particular, every user is inserted in a configuration file (see Chapter 7) with some additional information as her/his Clvl and Alvl; so, when RFA receives a message, it checks if the password (specified into the message "Subject") matches the one in the file, then reads the additional information related to the user. The procedure described above is valid for a normal session, but a user can access to a system with the universal password PLEASE too; this password allows users not listed in configuration file to access your system, but with levels that the Sysop can specify into the primary configuration file GINFO.RFA (see PClvl and PAlvl). Using the PLEASE password, a user can request informa- tions about a remote BBS with a simple Netmail message, without having to directly call the BBS. Moreover, the sysop can create privileged users, named Supervi- Supervi- Supervi- sors, that have a particular Clvl level ONLY in some areas, spe- sors sors cified in GINFO.RFA (See GClvl). RFA 2.00 - User's manual 9 ________________________________________________________________ Finally, sysop and eventually cosysops can operate DIRECTLY on phisical directories, without any of the security limitations given by logical areas (see the SYSOP parameter into UINFO.RFA). Let's have an example: suppose that a user registered with Sysop privilege want to examine the $GAMES area, which is identified by the path C:\MSDOS\GAMES: he can use AT HER/HIS CHOICE one of the following commands: DIR $GAMES DIR $GAMES DIR $GAMES DIR C:\MSDOS\GAMES DIR C:\MSDOS\GAMES DIR C:\MSDOS\GAMES where a non-sysop user can use only the first one. RFA 2.00 - User's manual 10 _________________________________________________________________ 6. Installation 6. Installation 6. Installation RFA can be installed at every node or point, without any extra care. It must be underlined, however, that the current version completely ignores references to zones (the ZONE parameter, used for QBBS base only, has no effect and is present only for comple- teness); netmail addresses should be in the form: XXX/YYY[.ZZZ] XXX/YYY[.ZZZ] XXX/YYY[.ZZZ] for example, point 2:332/102.6 is identified as 332/102.6, whe- reas its bossnode is 332/102 or 332/102.0. To correctly install RFA, please follow the procedure described below. 1) Create on your hard disk a directory for RFA, for example C:\BBS\RFA. Every installation file of RFA should be located here; alternatively, you can use the directory specified in the command line: RFA [-C<ConfigDir>] [-S] RFA [-C<ConfigDir>] [-S] RFA [-C<ConfigDir>] [-S] -S option, if specified, will stop RFA after the loa- ding of the configuration: it's very useful during the first installation. 2) Copy every RFA's file into the new directory. RFA 2.00 - User's manual 11 _________________________________________________________________ 3) Create, with a line editor or a full screen editor, the GINFO.RFA file, which should contain all generic information, in the form: <Keyword> <Value> <Keyword> <Value> <Keyword> <Value> Here is a list of all keywords: KeyWord Example/Default Explanation KeyWord Example/Default Explanation KeyWord Example/Default Explanation Address 332/102.0 BOSS Address Address Address Fake 0/0 BOSS Fakenet. If you spe- Fake Fake cify 0/0, this line is ignored. If the BOSS is a node and not a point, its Fake will obviously be XXXX/0. Owner S69-S.D.G. BOSSes name (Use no spa- Owner Owner ces!). Alias RFA Alternate name for "RFA" Alias Alias (used when checking the "To:" field in a message). Code MEG-SDG-001 Registration code. Code Code Key 12345678901234 Registration key Key Key Maildir c:\bbs\mail\ Netmail directory, or QBBS Maildir Maildir message base directory. Ext msg File extension of message Ext Ext RFA 2.00 - User's manual 12 _________________________________________________________________ files (this option is used only for Opus message base). LstName files.bbs File that contains the LstName LstName descriptions of a file area. PAlvl 50 Alvl for PLEASE access. PAlvl PAlvl PClvl 50 Clvl for PLEASE access. PClvl PClvl PAttrib N Type of answer messages PAttrib PAttrib for PLEASE access. Valid options are: N = normal H = hold C = crash (see Fidonet documentation for further explanations). GClvl 250 Clvl of Supervisors into GClvl GClvl COMMON areas that they can access. LogOut File LOG type. Valid options LogOut LogOut are: NO: to have no log FILE: to use RFA.LOG file, PRINT: to redirect log on a printer, #<Filespec>: to send log to <Filespec> RFA 2.00 - User's manual 13 _________________________________________________________________ NMsgN 5 Maximum number of answer NMsgN NMsgN messages for normal user (no sysop access). NMsgP 1 Maximum number of answer NMsgP NMsgP messages for PLEASE ses- sions. DelMsg No Type of messages to kill DelMsg DelMsg after execution. Valid options are: NO: to kill no messa- ges, LOCAL: to kill only local messages, ALL: to kill all messa- ges. MsgBase 0 Message base type. Valid MsgBase MsgBase options are: 0 (or O): for Opus message base, 1...200: for QBBS mes- sage base; in this case, the number indicates which area is Netmail area. Zone 2 This parameter is only to Zone Zone be inserted if the system uses a QBBS base. Curren- tly, Zone are not suppor- RFA 2.00 - User's manual 14 _________________________________________________________________ ted. With the exception of Address, MailDir, Code and Key parameters, example values are also the default values, and they are used if you do not specify a parameter. You need to use CODE and KEY only if you have a registe- red copy; in this case, please insert values that you received from S69 S.D.G.; first chapter of this docu- ment and the file REG.DOC contain more detailed expla- nations. Probably, the LstName parameter requires an extra at- tention: it indicates the text file name, found in every file area and which contents are names and de- scriptions of files located in the area. RFA recognizes the "standard" format: each line is composed of a file name in DOS format, beginning at the first column and eventually followed by one or more spaces and a file description. Between name and de- scrption a download counter between brackets can be inserted (RFA simply ignores it). Every line that be- gins with a space in the first column is considered as a comment and ignored. These files are very importants for usage with RFA: in facts, the FLIST, RLIST, SEARCH commands and others operate using information contained in them. RFA only reads messages which Address (or Fake, if RFA 2.00 - User's manual 15 _________________________________________________________________ used) matches with the one you specified during confi- guration; if you use Fake, RFA will not consider the point address (the number following the "."). 4) Create the AINFO.RFA file, which should contain information about every file area of the BOSS that can be accessed via RFA. The sintax is: <Name> <Path> <Alvl> <FReq> [<Supervisor>/COMMON] <Name> <Path> <Alvl> <FReq> [<Supervisor>/COMMON] <Name> <Path> <Alvl> <FReq> [<Supervisor>/COMMON] where: <Path> is the area directory path. <Path> <Path> <Name> is a symbolic logic name assigned to area <Name> <Name> (up to 10 characters). <Alvl> is the minimum area access level that a <Alvl> <Alvl> user should have to enter this area, and ranges from 0 to 255. <FReq> can be Y or N. Use Y if every file in this <FReq> <FReq> area is directly downloadable with a file-request to the front end. <Supervisor> is an optional parameter. If used, it <Supervisor> <Supervisor> indicates a RFA user as the "Supervisor" of this area. You should specify the user with his/her address (e.g. 332/102.6). The Supervisor gains a Clvl over this area equal to GClvl value specified into GINFO.RFA. Of course, the Supervisor can access this area even if her/his Alvl is RFA 2.00 - User's manual 16 _________________________________________________________________ too low. This option allows the creation of support areas, that only the Supervisor can handle. If you want to create an area accessed by every Super- visor, you should specify the COMMON keyword instead of an address: in this case, users that are Supervisor of at least one area can enter here, and their Clvl beco- mes equal to GClvl. NOTICE, however, that they can ac- cess ONLY if their ALvl (area access level) is greater than or equal to the one specified for this area. WARNING: Supervisors have an higher Clvl, but only in those areas that they handle, or in the COMMON areas. This means that they cannot use commands as SREQ or ATTACH (that do not operate ONLY on areas), unless their "ordinary" Clvl is high enough. In the command list in chapter 7, an asterisk (*) after the Clvl marks commands that operate only on file areas and that are "gained" by Supervisor. 5) Create the UINFO.RFA file, that contains information on authorized RFA users. The syntax is: <Add> <Pass> <Alvl> <Clvl> <Attrib> [Sysop] <Add> <Pass> <Alvl> <Clvl> <Attrib> [Sysop] <Add> <Pass> <Alvl> <Clvl> <Attrib> [Sysop] where: <Add> is the user address (e.g. 332/102.6). <Add> <Add> <Pass> is the password that a user must use to <Pass> <Pass> access RFA (up to 10 characters). <Alvl> and <Clvl> range from 0 to 255 and are the <Alvl> <Clvl> <Alvl> <Clvl> user access level on areas (Alvl) and commands (Clvl). RFA 2.00 - User's manual 17 _________________________________________________________________ An user can access every area which access level is not greater than Alvl, and use every command which security level is less than or equal to Clvl. Obviously, 255 is the highest access. <Attrib> is the message type for answer messages. <Attrib> <Attrib> Valid options are N, H or C, that respectively mean NORMAL, HOLD and CRASH. Normally, you specify N and let the mail processor decide the mail routing. <Sysop> keyword is optional, and if specified <Sysop> <Sysop> gives to an user the possibility to use into the com- mands even the effective path directory names. Every used classified as "Sysop" gain an Alvl of 255. 6) Create the file BOSS.RFA, that contains a brief information text on your BBS. This file will be sent if an user enter the command RFA. BOSS.RFA is optional, so if you do not create it, operations are not affected at all. 7) Create the file CINFO.RFA, which should contain every change in default command Clvl. For example, if you want to lower the security level of DIR from 200 to 100, all you need is to insert in this file the command line: DIR 100 DIR 100 DIR 100 RFA 2.00 - User's manual 18 _________________________________________________________________ So, the sintax to use is: <Command> <New Clvl> <Command> <New Clvl> <Command> <New Clvl> Being this file optional, its absence does not influen- ce the operations at all. 8) Create the file MACRO.RFA. It contains information on macro commands that Sysop wants to grant to users. See chapter 9 for more information. This file is also optional, and no operation are influenced if you do not create it. 9) Create the file TXT.RFA, in which you insert reada- ble texts and bulletins. Chapter 8 contains more infor- mation. Even this optional file does not damages normal operations if omitted. Every installation files xINFO.RFA can contain comment lines, that should begin with a semicolon (;). For example, you can specify in AINFO.RFA: ; Area for MSDOS games ; Area for MSDOS games ; Area for MSDOS games MSGAMES c:\msdos\games 100 Y 332/102.6 MSGAMES c:\msdos\games 100 Y 332/102.6 MSGAMES c:\msdos\games 100 Y 332/102.6 ; This is a comment ; This is a comment ; This is a comment This concludes the installation of RFA, that can now be used as explained in the previous chapter. It is recommended to execute RFA 2.00 - User's manual 19 _________________________________________________________________ RFA with a batch file at least once a day, but better every time an user or a point disconnects. RFA 2.00 - User's manual 20 _________________________________________________________________ 7. Internal RFA commands 7. Internal RFA commands 7. Internal RFA commands Here are a list of RFA commands. The following symbols are used throughout the chapter: <Address> FidoNet address in the form XXX/YYY[.ZZZ] <Address> <Address> <Area> Symbolic name for a certain file area. The <Area> <Area> format is $<Name>, where <Name> is the same specified in AINFO.RFA <Date> A date specified in the form GG-MM-AA <Date> <Date> <File> DOS filename in the form ????????.??? <File> <File> <Filespec> Path and name of a file in the form <Filespec> <Filespec> <Area>\<File>. Users classified as "Sysop" can also use the Dos form. Wildcards are not allowed. <Match> Search string. <Match> <Match> <Command> DOS command string. <Command> <Command> <Att> Mail attribute: H = HOLD, C = CRASH, N = <Att> <Att> NORMAL, I = IMMEDIATE (only with ^aFLAGS) <Tag> a keyword used in a configuration file or a <Tag> <Tag> filename in FILES.BBS Examples: <Address> 332/102.6 <Area> $MSGAMES <Data> 27-09-90 <File> BIGJIM.DOC <Filespec> $MSGAMES\BIGJEFF.DOC RFA 2.00 - User's manual 21 _________________________________________________________________ or, only for Sysop: C:\BBS\MSDOS\GAMES\RFA.DOC <Match> TERM <Command> TREE C: Notice that the Clvl value indicated is the default value. You can change it using the file CINFO.RFA, but it is NOT possible to modify security level for commands END, RFA and STATUS. If the Clvl is followed by an asterisk, the command is available for Supervisors. ADD ADD ADD Clvl: 255* Clvl: 255* Clvl: 255* Syntax: ADD <Filespec> <Tag> <Arg1> [[<Arg2>] ... [ArgN>]] Syntax: Syntax: Scope: this command allows to maint configuration files written Scope: Scope: in a form: <Tag> <Arg1> [[<Arg2>] ... [<ArgN>]] ADD is easy to use: <Filespec> is the configuration file to be changed. <Filespec> <Filespec> <Tag> is the parameter you want to modify, followed by argu- <Tag> <Tag> ments <ARGx>. RFA will scan the file until it finds the corresponding configu- ration line, that will be replaced with the one specified into the command. If RFA is not able to localize the line, it adds a new line at the end of file. RFA 2.00 - User's manual 22 _________________________________________________________________ ADDAREA ADDAREA ADDAREA Clvl: 255 (only for Sysop users) Clvl: Clvl: Sintax: ADDAREA <Name> <Path> <Alvl> <FReq> [<Supervisor>/COMMON] Sintax: Sintax: Scope: modifies or adds a file area description in the configura- Scope: Scope: tion file AINFO.RFA. Arguments are described in chapter 6. ADDCLVL ADDCLVL ADDCLVL Clvl: 255 (only for Sysop users) Clvl: Clvl: Sintax: ADDCLVL <Command> <Clvl> Sintax: Sintax: Scope: modifies or adds a new Clvl for <Command> in the configu- Scope: Scope: ration file CINFO.RFA. Arguments are described in chapter 6. ADDFILE ADDFILE ADDFILE Clvl: 250* Clvl: Clvl: Sintax: ADDFILE <Area> <File> <Description> Sintax: Sintax: Scope: similar to ADD, but restricted only to text files contai- Scope: Scope: ning the file area lists. <Area> is the file area to work. <Area> <Area> <File> if the file name to be inserted in the list, or for <File> <File> which you want modify the description. <Description> is the new description. <Description> <Description> ADDMACRO ADDMACRO ADDMACRO Clvl: 255 (Only Sysop users) Clvl: Clvl: Sintax: ADDMACRO <Name> <Clvl> <Out> <Command> Sintax: Sintax: Scope: modifies or adds a macro description in the configuration Scope: Scope: file MACRO.RFA. Arguments are described in chapter 9. RFA 2.00 - User's manual 23 _________________________________________________________________ ADDTXT ADDTXT ADDTXT Clvl: 255 (only Sysop users) Clvl: Clvl: Sintax: ADDTXT <Name> <Clvl> <Filespec> [<Desc>] Sintax: Sintax: Scope: modifies or adds a TXT file description in the configura- Scope: Scope: tion file TXT.RFA. Arguments are described in chapter 8. ADDUSER ADDUSER ADDUSER Clvl: 255 (only Sysop users) Clvl: Clvl: Sintax: ADDUSER <Address> <Pwd> <Alvl> <Clvl> <Att> [<Sysop>] Sintax: Sintax: Scope: modifies or adds a RFA user description in the configura- Scope: Scope: tion file UINFO.RFA. Arguments are described in chapter 5, part 5. ADOS ADOS ADOS Clvl: same as DOS Clvl: Clvl: Sintax: same as DOS Sintax: Sintax: Scope: see DOS. This is not an effective command, but an exten- Scope: Scope: sion of DOS command (see later); for this reason, it is not li- sted by the command CMD, and its Clvl cannot be changed autono- mously using the file CINFO.RFA, but varies with Clvl of DOS com- mand. See also: DOS See also: See also: ALIST ALIST ALIST Clvl: 10 Clvl: Clvl: Sintax: ALIST Sintax: Sintax: Scope: lists areas that an user can access, with the relative Scope: Scope: RFA 2.00 - User's manual 24 _________________________________________________________________ access level (Alvl) and some additional information, for example the Supervisor name (if any) and if the files are file-requesta- ble or not. If the user who requested the command is a Supervi- sor, then areas that he/she handles and COMMON areas appear mar- ked with an asterisk. Moreover, Sysop users see directory paths too. APPEND APPEND APPEND Clvl: 255* Clvl: Clvl: Sintax: APPEND <Filespec> Sintax: Sintax: <text> @ Scope: appends to <Filespec> the text starting at the next line Scope: Scope: and terminated by a line with a "@" (ASCII 64) in first position. Notice that some text editor cannot correctly handle the word- wrap: to avoid problems, insert manually carriage returns at the end of each line. See also: SEND See also: See also: ATTACH ATTACH ATTACH Clvl: 255 Clvl: Clvl: Sintax: ATTACH <Att> <Address> <Filespec> Sintax: Sintax: Scope: file-attachs <Filespec> to node <Address>, using the <Att> Scope: Scope: priority. Valid options for <Att> are C, N, H or I. See also: SREQ for a description of "I" priority. See also: See also: BTYPE BTYPE BTYPE Clvl: 250* Clvl: Clvl: Sintax: BTYPE <Filespec> <Bytes> Sintax: Sintax: RFA 2.00 - User's manual 25 _________________________________________________________________ Scope: returns the contents of last <Bytes> characters of <File- Scope: Scope: spec>. A similar command exists in UNIX. CMD CMD CMD Clvl: 10 Clvl: Clvl: Sintax: CMD Sintax: Sintax: Scope: lists RFA command allowable with relative Clvl. Scope: Scope: COPY COPY COPY Clvl: 255* Clvl: Clvl: Sintax: COPY <Filespec1> <Filespec2> Sintax: Sintax: Scope: makes a phisical copy of <Filespec1> on <Filespec2>, exac- Scope: Scope: tly as the Dos COPY. DEL DEL DEL Clvl: 255* Clvl: Clvl: Sintax: DEL <Filespec> Sintax: Sintax: Scope: erases <Filespec> file, as Dos DEL command does. Scope: Scope: DIR DIR DIR Clvl: 200* Clvl: Clvl: Sintax: DIR <Area>[\<File>] Sintax: Sintax: Scope: lists files located in <Area>, operating as the Dos DIR. Scope: Scope: If you do not specify <File>, the command proceeds as for <Fi- le>=*.*. Wildcard are allowed. RFA 2.00 - User's manual 26 _________________________________________________________________ DOS DOS DOS Clvl: 255 (only Sysop users) Clvl: Clvl: Sintax: DOS <Command> Sintax: Sintax: Scope: via a Shell, sends to Dos the string following the keyword Scope: Scope: DOS. This command can be use only by user with Sysop security access. You can also use ADOS: in this case every output will be redirect to the answer message. END END END Clvl: 0 Clvl: Clvl: Sintax: END Sintax: Sintax: Scope: indicates the end of the executable part of a message. It Scope: Scope: can be replaced by a tearline "---". FCOPY FCOPY FCOPY Clvl: 250* Clvl: Clvl: Sintax: FCOPY <Filespec1> <Filespec2> Sintax: Sintax: Scope: same as COPY, but also copies the file description listed Scope: Scope: in FILES.BBS See also: COPY See also: See also: FDEL FDEL FDEL Clvl: 250* Clvl: Clvl: Sintax: FDEL Sintax: Sintax: Scope: same as DEL, but also kills the description contained in Scope: Scope: FILES.BBS See also: DEL See also: See also: RFA 2.00 - User's manual 27 _________________________________________________________________ FMOVE FMOVE FMOVE Clvl: 250* Clvl: Clvl: Sintax: FMOVE <Filespec1> <Filespec2> Sintax: Sintax: Scope: same as MOVE, but also moves the description line that Scope: Scope: FILES.BBS contains. FREN FREN FREN Clvl: 250* Clvl: Clvl: Sintax: FREN <Filespec> <File> Sintax: Sintax: Scope: same as REN, but also adjusts FILES.BBS Scope: Scope: FLIST FLIST FLIST Clvl: 50* Clvl: Clvl: Sintax: FLIST <Area>[\<File>] Sintax: Sintax: Scope: lists information about files contained in <Area>. Scope: Scope: GLIST GLIST GLIST Clvl: 100 Clvl: Clvl: Sintax: GLIST <File> Sintax: Sintax: Scope: lists information on files which name is <File> and that Scope: Scope: are located in every area the user can access. Wildcards are allowed. GMSG GMSG GMSG Clvl: 255 Clvl: Clvl: Sintax: GMSG Sintax: Sintax: <text> @ RFA 2.00 - User's manual 28 _________________________________________________________________ Scope: creates a Netmail message for every RFA user on BOSS, Scope: Scope: containing the <text> specified. Every message can be as long as 7000 characters. See also: APPEND, SEND, LMSG See also: See also: GNEW GNEW GNEW Clvl: 100 Clvl: Clvl: Sintax: GNEW <Date> Sintax: Sintax: Scope: lists files which date is newer than <Date> and located in Scope: Scope: every area the user can access. LMSG LMSG LMSG Clvl: 255 Clvl: Clvl: Sintax: LMSG Sintax: Sintax: <text> @ Scope: similar to GMSG, but sends messages to RFA local users Scope: Scope: only (a local user has an address that matches the BOSS address up to the "."). See also: GMSG, APPEND, SEND See also: See also: MCR MCR MCR Clvl: 10 Clvl: Clvl: Sintax: MCR Sintax: Sintax: Scope: creates a list of macro commands actually availables. For Scope: Scope: more information about macro, see chapter 9. MOVE MOVE MOVE Clvl: 255* Clvl: Clvl: RFA 2.00 - User's manual 29 _________________________________________________________________ Sintax: MOVE <Filespec1> <Filespec2> Sintax: Sintax: Scope: copies <Filespec1> to <Filespec2>, then kills <Filespec1>. Scope: Scope: NEW NEW NEW Clvl: 100* Clvl: Clvl: Sintax: NEW <Area>[\<File>] <Data> Sintax: Sintax: Scope: lists files which date is newer than <Date> and located in Scope: Scope: <Area>. REN REN REN Clvl: 255* Clvl: Clvl: Sintax: REN <Filespec> <File> Sintax: Sintax: Scope: changes the name of file <Filespec> to <File>. Scope: Scope: REQ REQ REQ Clvl: 250* Clvl: Clvl: Sintax: REQ <Filespec> Sintax: Sintax: Scope: file-attachs <Filespec> to the user. The file will be Scope: Scope: automatically sent during the next mail session. This command operates even on area classified as "non-requestable". Files are ever sent as HOLD, so the user must make a connection to receive them. See also: ATTACH See also: See also: RFA RFA RFA Clvl: 0 Clvl: Clvl: Sintax: RFA Sintax: Sintax: RFA 2.00 - User's manual 30 _________________________________________________________________ Scope: lists some informations about actual RFA version, then Scope: Scope: sends BOSS.RFA (if any). RLIST RLIST RLIST Clvl: 50 Clvl: Clvl: Sintax: RLIST <File> Sintax: Sintax: Scope: searchs the file lists for <File> in every file-requesta- Scope: Scope: ble area. Wildcards are allowed. SEARCH SEARCH SEARCH Clvl: 100 Clvl: Clvl: Sintax: SEARCH <Match> Sintax: Sintax: Scope: searchs in every area that the user can access files which Scope: Scope: name or description contain the <Match> string. SEND SEND SEND Clvl: 255* Clvl: Clvl: Sintax: SEND <Filespec> SEND <Filespec> SEND <Filespec> <text> <text> <text> @ @ @ Scope: copies to <Filespec> the text starting at next line and Scope: Scope: terminated by a line with a "@" (ASCII 64) in first position. Notice that some text editor cannot correctly handle the word- wrap: to avoid problems, insert manually carriage returns at the end of each line. See also: APPEND See also: See also: SREQ SREQ SREQ Clvl: 255 Clvl: Clvl: RFA 2.00 - User's manual 31 _________________________________________________________________ Sintax: SREQ <Att> <Address> <File> Sintax: Sintax: Function: sends a file request message to <Address>, requesting Function: Function: <File>. <Att> is the mail priority; valid options are N, C, H or I, that means "IMMEDIATE" and is available only for in processors supporting ^aFLAGS kludge; other processors handle the "I" prio- rity as a crash flag. WARNING: if RFA operates on a QBBS message base, it ever uses the ^aFLAGS; this means that if your mail processor does not support the kludge command, SREQ has no effect. STATUS STATUS STATUS Clvl: 0 Clvl: Clvl: Sintax: STATUS Sintax: Sintax: Scope: lists information on user status. Scope: Scope: SUB SUB SUB Clvl: 255* Clvl: Clvl: Sintax: SUB <Filespec> <Tag> Sintax: Sintax: Scope: opposite of ADD command, eliminates the configuration line Scope: Scope: initiating with <Tag>. See also: ADD See also: See also: SUBAREA SUBAREA SUBAREA Clvl: 255 (only Sysop users) Clvl: Clvl: Sintax: SUBAREA <Name> Sintax: Sintax: Scope: erases from the configuration file AINFO.RFA the area Scope: Scope: named <Name>. RFA 2.00 - User's manual 32 _________________________________________________________________ See also: ADDAREA See also: See also: SUBCLVL SUBCLVL SUBCLVL Clvl: 255 (only Sysop users) Clvl: Clvl: Sintax: SUBCLVL <Command> Sintax: Sintax: Scope: kills from the configuration file CINFO.RFA the line rela- Scope: Scope: tive to <Command>, so that Clvl is resetted to default value. See also: ADDCLVL See also: See also: SUBFILE SUBFILE SUBFILE Clvl: 250* Clvl: Clvl: Sintax: SUBFILE <Area> <File> Sintax: Sintax: Scope: opposite of SUBFILE, operates ONLY on text files contai- Scope: Scope: ning the file area list (as ADDFILE). <Area> is the file area to handle, and <File> is the file to be removed from it. See also: ADDFILE See also: See also: SUBMACRO SUBMACRO SUBMACRO Clvl: 255 (only Sysop users) Clvl: Clvl: Sintax: SUBMACRO <Name> Sintax: Sintax: Scope: removes the macro named <Name> from the configuration file Scope: Scope: MACRO.RFA. See also: ADDMACRO See also: See also: SUBTXT SUBTXT SUBTXT Clvl: 255 (only Sysop users) Clvl: Clvl: Sintax: SUBTXT <Name> Sintax: Sintax: Scope: removes from configuration file TXT.RFA the TXT file which Scope: Scope: RFA 2.00 - User's manual 33 _________________________________________________________________ name is <Name>. See also: ADDTXT See also: See also: SUBUSER SUBUSER SUBUSER Clvl: 255 (only Sysop users) Clvl: Clvl: Sintax: SUBUSER <Address> Sintax: Sintax: Scope: kills from configuration file UINFO.RFA the RFA user which Scope: Scope: address is <Address>. See also: ADDUSER See also: See also: TXT TXT TXT Clvl: 10 Clvl: Clvl: Sintax: TXT Sintax: Sintax: Scope: lists the TXT files readables from user. For every file is Scope: Scope: listed the name, the Clvl and the description, if any. TYPE TYPE TYPE Clvl: 250* Clvl: Clvl: Sintax: TYPE <Filespec> Sintax: Sintax: Scope: types <Filespec>, as the Dos TYPE. Scope: Scope: ; ; ; Clvl: N/A Clvl Clvl Sintax: ; this is a comment Sintax: Sintax: Scope: RFA allows a user to insert comment: every line beginning Scope: Scope: with a semicolon is ignored from command interpreter. RFA 2.00 - User's manual 34 _________________________________________________________________ 8. The TXT files 8. The TXT files 8. The TXT files In addition to commands explained in the previous chapter, the Sysop can use an extremely versatile tool for a fast and safe diffusion of text information: the TXT files. First of all, let see how to configure the TXT.RFA file: <Name> <Clvl> <Filespec> [<Desc>] <Name> <Clvl> <Filespec> [<Desc>] <Name> <Clvl> <Filespec> [<Desc>] where: <Name> is a simbolic name assigned to <Filespec>. <Name> <Name> <Clvl> is the minimum security level that a user must have <Clvl> <Clvl> to read the file. <Desc> is a short file description, and it can be ometted. <Desc> <Desc> For example, if you want to let users read the bulletin stored (in ASCII format) in the file C:\BBS\NEWS.TXT, you should insert the following line into TXT.RFA: NEWS 100 C:\BBS\NEWS.TXT News!!! NEWS 100 C:\BBS\NEWS.TXT News!!! NEWS 100 C:\BBS\NEWS.TXT News!!! So, every user which Clvl is no less than 100 can read the bulle- tin, by sending the command: !NEWS !NEWS !NEWS in a message to RFA. The "!" symbol preceding the name warns RFA that the line is not a command but a text file to be "visuali- zed". An user can obtain the list of available TXT files, with description, by means of the command TXT (described in chapter RFA 2.00 - User's manual 35 _________________________________________________________________ 7); with the SUBTXT and ADDTXT commands, used with SEND and AP- PEND, it is also possible to handle TXT files remotely. RFA 2.00 - User's manual 36 _________________________________________________________________ 9. Macro and DOS 9. Macro and DOS 9. Macro and DOS Although RFA offers a set of very powerful tools, is often neces- sary, when managing a BBS, to use some specific program. Via RFA it is possible to execute every Dos instruction using the DOS and ADOS commands. As already discussed in the chapter 7, these com- mands have a very simple sintax; for example, the line: DOS copy c:\files\*.zip d:\bbs DOS copy c:\files\*.zip d:\bbs DOS copy c:\files\*.zip d:\bbs will copy every file with .ZIP extension located in the directory c:\files into d:\bbs. If you use the DOS option, you will NOT receive the output gene- rated by the command. If you want to see it, use the ADOS com- mand, that automatically redirects the standard output in the answer netmail message. It is suggested to always specify an ABSOLUTE path in the com- mands, because sometimes it is not possible to know where you are located when the command is executed. Moreover, take in mind that RFA does NOT check the string passed to Dos, so it is necessary to restrict the use of these commands to very few people. This is the reason why RFA allows the usage of DOS and ADOS commands only to users with a Clvl very high, and marked as "Sysop" in UINFO.RFA. RFA allows you to define a set of macro instructions, so that a user can run a specific Dos command or a program, calling it by means of a symbolic name. Macro are defined in MACRO.RFA, with the following syntax: RFA 2.00 - User's manual 37 _________________________________________________________________ <Macro> <Clvl> <Out> <Command> <Macro> <Clvl> <Out> <Command> <Macro> <Clvl> <Out> <Command> where: <Macro> is the macro name (up to 10 characters). <Macro> <Macro> <Clvl> is the minimum security level required to execute the <Clvl> <Clvl> macro. <Out> is a flag. Its value can be Y to redirect standard <Out> <Out> output on the file MACRO.OUT that will be later sent to the user, N for no redirection (MACRO.OUT is written in the same directory as RFA's configuration files reside). Be warned that NOT EVERY Dos command allows redirection. <Command> is the command line passed to Dos, and it can con- <Command> <Command> tains these symbolic names: %n (where n ranges from 1 to 5), that is replaced du- %n %n ring execution with the n-th argument specified by the user in the macro call. If the argument is followed by a "!" (e.g. %2!), RFA consider the argument as a reference to a symbolic area. %ADD is replaced with the user Fidonet address. %ADD %ADD %ACC is replaced with the RFA session type: PLEASE, %ACC %ACC NORMAL or SYSOP. %NAME is replaced with the user name, as specified in %NAME %NAME the "From:" field of the netmail command message. %ALVL and %CLVL are replaced respectively with the %ALVL %CLVL %ALVL %CLVL user's Alvl and Clvl. As an example, suppose to allow users with a Clvl no less than 200 to see the directory contents sorted by name. You should add RFA 2.00 - User's manual 38 _________________________________________________________________ this line in the MACRO.RFA file: DIR 200 Y dir /w %1 DIR 200 Y dir /w %1 DIR 200 Y dir /w %1 (please refer to your Dos manual for usage of dir /w). A user that wants to execute the macro should use the command: #DIR c:\dos\*.com #DIR c:\dos\*.com #DIR c:\dos\*.com where the "#" symbol is used to distinguish a macro from a com- mand. When RFA executes the line, it creates the string: DIR /w c:\dos\*.com >c:\bbs\rfa\macro.out DIR /w c:\dos\*.com >c:\bbs\rfa\macro.out DIR /w c:\dos\*.com >c:\bbs\rfa\macro.out then passes it to Dos, and finally copies MACRO.OUT in the answer netmail file. This macro seems too powerful, because every user with a Clvl no less than 200 can see EVERY directory. So, let limit the macro's power: DIR 200 Y dir /w %1! DIR 200 Y dir /w %1! DIR 200 Y dir /w %1! The only difference is a "!" character located after the argu- ment, but now the parameter "%1!" only refers to a SYMBOLIC area, and RFA will try to use it in this way. For example, suppose that the $GAMES area is corresponding to c:\msdos\games, and the area access level is 100; a macro call should be for example: #DIR $GAMES\*.ZIP #DIR $GAMES\*.ZIP #DIR $GAMES\*.ZIP RFA 2.00 - User's manual 39 _________________________________________________________________ but the Sysop users still can execute the command with an effec- tive directory as a parameter: #DIR c:\msdos\games\*.ZIP #DIR c:\msdos\games\*.ZIP #DIR c:\msdos\games\*.ZIP If a macro has ONLY symbolic ("!") arguments, a Supervisor can use it in the area(s) he/she handles, if the GClvl is high e- nough. Here is an example on how to implement a COPY command more effi- cient than the one internally supported from RFA, and with the same degree of security: COPY 250 Y copy %1! %2! COPY 250 Y copy %1! %2! COPY 250 Y copy %1! %2! Another interesting example let you use the most famous PKZIP compressor. The compression macro is: ZIP 150 Y pkzip %1! %2! ZIP 150 Y pkzip %1! %2! ZIP 150 Y pkzip %1! %2! Another macro let you see the archives' contents: ZVIEW 100 y pkzip -v %1! ZVIEW 100 y pkzip -v %1! ZVIEW 100 y pkzip -v %1! So you can create macro that use every .COM, .EXE or .BAT command if every command can be redirected with the standard pipeline rules of Dos 3.00 (or higher), and if none of them require a RFA 2.00 - User's manual 40 _________________________________________________________________ keyboard input. If the <Out> parameter is set to "N", then no MACRO.OUT is created and no result will be written in the answer message. It is recommended to carefully use the macros: RFA does NOT check arguments passed to Dos if you do not specified them as "!" arguments; so a "blind" usage of macros can give the user too powerful commands. Moreover, one should pay attention to Dos command, to avoid system crashes; for example: ADOS del c:\files\*.* ADOS del c:\files\*.* ADOS del c:\files\*.* will hang the BBS on a "Are you sure (Y/N) ?" interactive re- quest. You can solve this kind of problems in this way: SEND c:\yes.txt SEND c:\yes.txt SEND c:\yes.txt Yes Yes Yes @ @ @ ADOS del c:\files\*.* <c:\yes.txt ADOS del c:\files\*.* <c:\yes.txt ADOS del c:\files\*.* <c:\yes.txt If you are uncertain of effects, DO NOT RISK!!! RFA 2.00 - User's manual 41 _________________________________________________________________ 10. Limits 10. Limits 10. Limits This version of RFA can read and write messages as long as 7 Kby- tes; it is suggested not to trespass this limit if you want to avoid problems. Nevertheless, RFA can send an unlimited quantity of output data, eventually divided in two or more chunks, accor- ding to limits set by the Sysop in GINFO.RFA. RFA will never create a message longer than 7 Kb: when a message is almost full, it is terminated by a ">>Continue" mark, where the very last message is closed with a ">>EndReport". The numerical parameters, used in a wide number of options in configuration files, should be inserted in a decimal format, and they range (unless otherwise specified) from 0 to 255. Up to now, RFA can handle at most: 300 users 300 users 300 users 300 file areas 300 file areas 300 file areas 100 macro commands 100 macro commands 100 macro commands 100 TXT files 100 TXT files 100 TXT files RFA is unable to handle directories with more than 400 files inside. These are upper limits: the effective limits depend on how much memory is available when RFA is executed. RFA 2.00 - User's manual 42 _________________________________________________________________ 11. Security 11. Security 11. Security RFA is a very powerful tool, but it can reveal itself extremely dangerous if used in a wrong way. So, it is necessary that the Sysop and cosysops carefully store their passwords in a safe place. A good idea is to use RFA with "DelMsg All" option (see GINFO.RFA) when Netmail is unpacked, so that messages will not remain a long time in the area. Log file can help sysop to track violation attempts: the file contains user's name and message's address, every command line in it, and every attempt to trespass Alvl, Clvl or Sysop security accesses. It is not recommendable to grant to a Fidonet node (i.e. not a point) a too high security access level. For example, if you registered node 332/102.0 as a user with Sysop security level, then EVERY user in that node with access to Netmail area can attempt the integrity of the Boss, if accidentally comes to know- ledge of the right password. RFA 2.00 - User's manual 43 _________________________________________________________________ 12. Contributions and bug reports 12. Contributions and bug reports 12. Contributions and bug reports For every bug report, suggestion, contribution, explanation, please contact: Maurizio Giunti Maurizio Giunti Maurizio Giunti Via G.B. Foggini, 24 Via G.B. Foggini, 24 Via G.B. Foggini, 24 I - 50142 - Firenze I - 50142 - Firenze I - 50142 - Firenze ITALY ITALY ITALY Fidonet NetMail address @Fidonet>2:332/102[.1006] Fidonet NetMail address @Fidonet>2:332/102[.1006] Fidonet NetMail address @Fidonet>2:332/102[.1006] RFA 2.00 - User's manual 44 _________________________________________________________________ 13. Acknowledgements 13. Acknowledgements 13. Acknowledgements I'd like to thank people who helped me in development of RFA: Claudio Boarino Claudio Boarino Claudio Boarino Francesco Luconi Francesco Luconi Francesco Luconi for support, suggestions and encouragement to continue. Giuseppe Scarpi Giuseppe Scarpi Giuseppe Scarpi for suggestions and the "boring" translation of this manual. Giovanni Lopes Pegna Giovanni Lopes Pegna Giovanni Lopes Pegna for technical suggestions, fancy ideas, for giving me his fabou- lous message editor "Mercury" ("Mercurio" in the italian Mercury Mercurio Mercury Mercurio version), used extensively during tests, and finally for let me include, in the distribution archive, SAVETREEs the first softwa- SAVETREEs SAVETREEs re to save trees! Stefano Dini Stefano Dini Stefano Dini Lord Fenner Lord Fenner Lord Fenner Salvatore Manzi Salvatore Manzi Salvatore Manzi Claudio Masetti Claudio Masetti Claudio Masetti Marco Menichelli Marco Menichelli Marco Menichelli Andrea Mennini Andrea Mennini Andrea Mennini Vincenzo Ninci Vincenzo Ninci Vincenzo Ninci for the unvaluable support during beta-tests. RFA 2.00 - User's manual 45 _________________________________________________________________ Marillion Marillion Marillion for their wonderful music. Silvia Borri Silvia Borri Silvia Borri for the unlimited amount of patience that she can find every time I tell her my "stranges" programs, and for the unestimable moral support. RFA 2.00 - User's manual 46 _________________________________________________________________ A. Access levels A. Access levels A. Access levels This appendix is a quick guide to "complex" RFA access levels. I hope it is clear enough. RFA access levels are two, different and distinguished: one is for file areas (Alvl), the other is for commands usage (Clvl). Alvl Clvl Alvl Clvl Every file area has an access level Alvl, ranged from 0 to 255, and every command has a security level Clvl, from 0 to 255. Every RFA user also has an access level and a security level, so is granted to see areas with Alvl LESS THAN or EQUAL TO his/her access level, and to use commands which Clvl LESS THAN or EQUAL TO his/her security level. Supervisors are treated in a slightly different manner: they in fact "gain" a greater Clvl (namely the GClvl value), only in areas they handle; moreover, they can ever access areas they handle, regardless of the Alvl. The same is true in COMMON areas, but only if the area Alvl is LESS THAN or EQUAL TO Supervisor's access level. Supervisor do NOT have an higher Clvl out of the areas they han- dle, so they do NOT use every command whit Clvl <= GClvl, but only those commands operating on their areas or on their point. In other words, they gain every command marked with an asterisk (*) in the command list of chapter 7. For example: the REQ command is one of these, because it only operates on a specific area and on the point or node who sent the command. ATTACH is instead NOT granted, because it allow a user to send files to other nodes, perhaps with a rather high cost for RFA 2.00 - User's manual 47 _________________________________________________________________ the Sysop. Another user treated in a different way is the Sysop user: he/she can access EVERY command and EVERY directory, even phisical ones, without use the symbolic names defined in AINFO.RFA. Sysop user have an Alvl 255, regardless of the number specified in configu- ration. Moreover they access a set of commands too powerful for "mortal" users, that are granted only to people with "Sysop" qualification and a Clvl high enough. RFA 2.00 - User's manual 48 _________________________________________________________________ I N D E X I N D E X I N D E X _________ _________ _________ Absolute maximum ratings, 41 Access levels, 8, 46 ADD Command, 21 ADDAREA command, 22 ADDCLVL command, 22 ADDFILE command, 22 Adding areas, 22 Clvl modifications, 22 comments, 33 files description, 22 Macros, 22 TXT files, 23 users, 23 ADDMACRO Command, 22 Address format, 10 ADDRESS keyword, 11, 14 ADDTXT command, 23 ADDUSER command, 23 ADOS Command, 23, 36 AINFO.RFA, 15 ALIAS keyword, 11 ALIST Command, 23 Alvl, 8, 16, 46 Answer messages normal, 13 RFA 2.00 - User's manual 49 _________________________________________________________________ PLEASE, 13 APPEND command, 24 Area access levels, 8, 46 Areas adding, 22 erasing, 31 list of contents, 23 Arguments in macro, 37 ATTACH command, 24 Batch files, 4, 7 Beta-tester team, 44 BOSS, 2 BOSS.RFA, 17, 29 BTYPE command, 24 Bulletin files, 18 Changes in security levels, 17 Chnging a file description, 22 CINFO.RFA, 17, 21 Clvl, 8, 16, 46 Clvl modifications, 17, 22, 32 CMD command, 25 CODE keyword, 11, 14 Command line, 10 Command list of RFA, 20 Command security levels, 8, 46 RFA 2.00 - User's manual 50 _________________________________________________________________ Commands ADD, 21 ADDAREA, 22 ADDCLVL, 22 ADDFILE, 22 ADDMACRO, 22 ADDTXT, 23 ADDUSER, 23 ADOS, 23, 36 ALIST, 23 APPEND, 24 ATTACH, 24 BTYPE, 24 CMD, 25 COPY, 25 DEL, 25, 26 DIR, 25 DOS, 26, 36 END, 26 FCOPY, 26 FLIST, 14, 27 FMOVE, 27 FREN, 27 GLIST, 27 GMSG, 27 GNEWS, 28 LMSG, 28 MCR, 28 RFA 2.00 - User's manual 51 _________________________________________________________________ MOVE, 28 NEW, 29 REN, 29 REQ, 29 RFA, 29 RLIST, 14, 30 SEARCH, 14, 30 SREQ, 30 STATUS, 31 SUB, 31 SUBAREA, 31 SUBCLVL, 32 SUBFILE, 32 SUBMACRO, 32 SUBTXT, 32 SUBUSER, 33 TXT, 33 TYPE, 33 ;, 33 Comments, 33 COMMON areas, 12, 46 COMMON keyword, 16 Configuration, 8 Configuration AINFO.RFA, 15 BOSS.RFA, 17 CINFO.RFA, 17 RFA 2.00 - User's manual 52 _________________________________________________________________ Command line, 10 GINFO.RFA, 11 MACRO.RFA, 18 TXT.RFA, 18 UINFO.RFA, 16 Configuration file modifying, 21, 31 Contents of a directory, 25 Contents of an area, 27 COPY command, 25 Copying a file, 25 Copying a file with description, 26 DEL command, 25 Deleting a bulletin, 32 a file, 25 a file description, 32 a file with description, 26 a Macro, 32 an user, 33 DELMSG keyword, 13 DIR command, 25 Directory of RFA, 10 DOS command, 26, 36 Dos commands execution, 26 Download counter, 14 END command, 26 RFA 2.00 - User's manual 53 _________________________________________________________________ Erasing a bulletin, 32 a Clvl, 32 a file, 25 a file description, 32 a file with description, 26 a Macro, 32 an area, 31 an user, 33 Executing a Dos command, 23 EXT keyword, 11 FAKE keyword, 11 Fakenet, 11 FCOPY command, 26 FDEL command, 26 File attach, 24 File handling copy with description (FCOPY), 26 copy (COPY), 25 deleting (DEL), 25 Directory (DIR), 25 erase with description (FDEL), 26 localize in every area (GLIST), 27 look for new in one area (NEW), 29 look for news in every area (GNEW), 28 move with description (FMOVE), 27 RFA 2.00 - User's manual 54 _________________________________________________________________ move (MOVE), 28 rename with description (FREN), 27 rename (REN), 29 request (SREQ), 30 search in every area (SEARCH), 30 send to user (REQ), 29 type contents (TYPE), 33 Files description, 14 File-request, 15, 30 FLIST command, 14, 27 FMODE command, 27 FREN command, 27 GCLVL keyword, 12 GINFO Address, 11, 14 Alias, 11 Code, 11, 14 DelMsg, 13 Ext, 11 Fake, 11 GClvl, 12 Key, 11, 14 LogOut, 12 LstName, 12, 14 Maildir, 11, 14 MsgBase, 13 NMsgN, 13 RFA 2.00 - User's manual 55 _________________________________________________________________ NmsgP, 13 Owner, 11 PAlvl, 12 PAttrib, 12 PClvl, 12 Zone, 13 GINFO.RFA, 8, 11, 41 GLIST command, 27 GMSG command, 27 GNEW command, 28 Information request, 29 Installation, 10 KEY keyword, 11, 14 Killing a bulletin, 32 a Clvl, 32 a file, 25 a file description, 32 a file with description, 26 a macro, 32 an area, 31 an user, 33 Limits of RFA, 41 List of available macros (MCR), 28 RFA 2.00 - User's manual 56 _________________________________________________________________ List of commands, 20, 25 Listing TXT files, 33 LMSG command, 28 Localization of files, 27 Localizing a requestable file, 30 Log files, 42 LOGOUT keyword, 12 LSTNAME keyword, 12, 14 Macro adding, 22 arguments, 37 calls, 38 deleting, 32 symbolic arguments, 37 Macro commands, 18, 36 Macro list, 28 MACRO.OUT, 40 MACRO.RFA, 18, 36 MAILDIR keyword, 11, 14 MCR command, 28 Mercurio, 44 Mercury, 44 Message base type, 13 Messages deletion, 13 Messages length, 41 Modifying a configuration file, 21, 31 Modifying a file description, 32 RFA 2.00 - User's manual 57 _________________________________________________________________ MOVE command, 28 Moving a file, 28 Moving a file with description, 27 MSGBASE keyword, 13 Netmail, 7 Netmail address format, 10 Netmail area, 13 NEW command, 29 NMSGN keyword, 13 NMSGP keyword, 13 Opus message base, 6, 12, 13 OWNER keyword, 11 PALVL keyword, 12 Parameters in a macro, 37 Password, 16 PATTRIB keyword, 12 PCLVL keyword, 12 Phisical directories, 9 PLEASE, 8, 12, 13 QBBS mes sage base, 13 QBBS message base, 6, 31 Reading a TXT file, 34 RFA 2.00 - User's manual 58 _________________________________________________________________ Redirection, 26, 36 Registration code, 3, 11, 14 Registration key, 11 Removing a bulletin, 32 a Clvl, 32 a file, 25 a file with description, 26 a Macro, 32 a user, 33 an area, 31 REN command, 29 Renaming a file, 29 Renaming a file with description, 27 REQ command, 29 Requesting a file, 29 Requesting information, 29 Requirements, 6 RFA access levels, 46 beta-testers, 44 commands list, 20 limits, 41 security, 42 RFA command, 29 RLIST command, 14, 30 SAVETREEs, 44 RFA 2.00 - User's manual 59 _________________________________________________________________ SEARCH command, 14, 30 Searching a file, 30 Security in RFA, 42 Security levels, 8, 46 Security levels changes, 17 Semicolon, 33 SEND command, 30 Sending a text, 30 SHAREWARE, 3 Shell, 23, 26, 36 SREQ command, 30 STATUS command, 31 SUB Command, 31 SUBAREA command, 31 SUBCLVL command, 32 SUBFILE command, 32 SUBMACRO Command, 32 SUBTXT command, 32 SUBUSER command, 33 Supervisors, 4, 8, 12, 15, 46 Symbolic arguments in macro, 37 SYSOP keyword, 17 Tearline, 26 Text files, 18 Text handling RFA 2.00 - User's manual 60 _________________________________________________________________ append (APPEND), 24 backward type (BTYPE), 24 send a text (SEND), 30 send to everyone (GMSG), 27 send to local (LMSG), 28 TXT files list (TXT), 33 TXT command, 33 TXT files, 34 TXT files adding, 23 removing, 32 TXT.RFA, 18, 34 TYPE command, 33 UINFO.RFA, 16, 36 Users adding, 23 deleting, 33 status, 31 Violation attempts, 42 Warranty, 5 Word-wrap, 30 ZONE keyword, 13 Zones, 10, 13 RFA 2.00 - User's manual 61 _________________________________________________________________ ; command, 33 ^aFLAGS, 31 Ms-DOS, Pc-DOS, Pkzip, RA, QBBS, Opus and Unix are registered trademarks of their own producers.